lean | Django Rest Framework Boilerplate and Pre | REST library

This is just a question related to OOP. Unity is not needed to be considered.

A constructor let you create an object instance and initialize the members of the object at the same time. If there are some immutable members (i.e. they will never be changed after construction), you may need to initialize them in constructors, and you may add the keyword readonly to the members. If you don't need to initialize any member with passing parameter(s) when the instance is created, there is no need to have a custom constructor (unless you want to hide the default constructor).

The access modifier protected makes the member accessible only in code in the same class, or in a class that is derived from that class. If you need to access the member in other places, you still need do it via public/internal methods such as setters and getters, or make it public/internal.

In your case, I think a constructor is needed to initialize the members such as player when a PlayerState instance is created.

Is there a preferred way to deal with a LocalTime that represents a 24 hours span?

It's worth taking a step back and separating different concepts very carefully and being precise. A LocalTime doesn't represent a 24 hour span - it's just a time of day. Two LocalTime values could effectively represent a 24 hour span without reference to a specific date, yes.

If you can possibly change your JSON to use 00:00:00, and then treat a "start==end" situation as being the full day, that's what I'd do. That does mean, however, that you can never represent an empty period.

Now, in terms of whether you should use a start and duration... that really depends on what you're trying to model. Are you trying to model a start time and an end time, or a start time and a duration? So far you've referred to the whole day as "a 24 hour span" but that's not always the case, if you're dealing with time zones that have UTC offset transitions (e.g. due to daylight saving time).

Transitions already cause potential issues with local intervals like this - if you're working on a date where the local time "falls back" from 2am to 1am, and you've got a local time period of (say) 00:30 to 01:30, then logically that will be "true" for an hour and a half of the day:

• 00:00-00:30: False
• 00:30-01:30 (first time): True
• 01:30-02:00 (first time): False
• 01:00-01:30 (second time): True
• 01:30-02:00 (second time): False
• 02:00-00:00 (next day): False

We don't really know what you're doing with the periods, but that's the sort of thing you need to be considering... likewise if you represent something as "00:00 for 24 hours" how does that work on a day which is only 23 hours long, or one that is 25 hours long? It will very much depend on exactly what you do with the data.

I would adopt a process of:

• Work out detailed requirements, including what you want to happen on days with UTC offset transitions in the specific time zone (and think up tests at this stage)
• Extract the logical values from those requirements in terms of Noda Time types (with the limitation that no, we unfortunately don't support 24:00:00 as a LocalTime)
• Represent those types in your JSON as closely as possible
• Make your code follow your requirements documentation as closely as possible, in terms of how it handles the data

In your run command, get rid of the "--debug --debugger-agent=transport=dt_socket,server=y,address=0.0.0.0:55555,suspend=y". This is trying to consume the same port which is why you are getting the address already in use error.

Running the debugger on a different port will also work as long as it isn't one of the ports you are exposing via docker.

Glad it works, thanks!

In this part, you're using callback syntax so articles is undefined

You should add the template tag inside your string. For example, if a = "123", would become .

Problem is you are using very old version of axios (0.2.0 ...from Sep 12, 2014)

If you update to current verison, it works...

bazel query --output=build //projX:all will print out all the targets in that package after macro and glob expansion. It has comments with the macro expansion stack traces for each target, including filenames and line numbers for the macro definitions.

//projX:all is form of wildcard which specifies all the targets in that package. Macros can only generate targets in a single package, so that will always include all targets generated from that macro invocation.

You may want to make a separate predefined subclass of Result for a default 'Success' result.

(I misinterpreted your question at first; in case one finds this question and is just looking for a way to disable PyCharm inspections locally or globally; scroll down).

E.g:

I don't see the categories mentioned in your code in the csv file you shared. In order to concat dataframes along columns, you could use pd.concat along axis=1. It concats the columns of same index number. So first set the Date column as index and then concat them, and then again bring back Date as a dataframe column.

• To set Date column as index of dataframe, df1 = df1.set_index('Date') and df2 = df2.set_index('Date')
• Concat the dataframes df1 and df2 using df_merge = pd.concat([df1,df2],axis=1) or df_merge = pd.merge(df1,df2,on='Date')
• bringing back Date into column by df_merge = df_merge.reset_index()