Alexander Droste

It definitely depends on the personal preference. I'd like to see different kinds/types to be visually separated. However i agree that prepending the kind to each item can be "too...

Same problem here. Private and protected members are not marked in any way.

@zanzlender Your solution neither works nor makes sense. You are just redirecting /en to /hr. I found a hacky solution with a custom middleware that redirects `/locale*` to `/*`. E.g....

@nmain True, to *really* fix this problem the whole community must adopt a new file extension. I just don't understand why they went with .ts in the first place. This...

While using tsx is definitely an option to circumvent the problems mentioned above it breaks semantic consistency. Using tsx in a context without jsx-elements will certainly lead to confusion when...

Thanks for the statement. I just wanted to raise awareness that file extension ambiguity is a thing (and it‘s annoying).

This is really easy @CharlesMcD @ryanf5. Like @navneet-g suggested: ```javascript const store = createDynamicStore({ // initialState: { }, // extensions, advancedCombineReducers: combineReducersWithReset }, /* core modules */ ); ``` and...

@NikolaStanisavljevic The workaround I use right now is to not make my styling depend on slick-current. If I just ignore it and use a custom-class or even slick-center the styling...

Push. Same here.

Wow, I can't believe that such a *crucial* thing is broken. Besides, this package just ignores the `// prettier-ignore` comment (see #26 ). So it's not even an option to...