[Extension Developers] Flarum 1.0 QA Phase Update Period

Qiaeru thank u so much.

i've noticed that i see a warning into console about:

index.js:36 Calling$.tooltipis now deprecated. Please use the<Tooltip>component exposed by flarum/core instead.$.tooltipmay be removed in a future version of Flarum.

but i have only one extension enabled, and i do not call old tooltip....so its related to core?

So the core is preprepared for this, but in the case of the extensions the genders would have to be previously defined by the extensions themselves? how would the extension know when to make the gender change?

Qiaeru Thank you

Darkle Genders aren't currently supported. The change of the translation system allows it to be possible in the future. Currently, extensions can implement their own genderization, however to affect the entirety of core they'd have to replace all the translations & when they are used... so not very feasible at the moment.

datitisev Ok that makes it so much easier, I thought I had to implement this as well, thanks!

Looks like my extensions discussion-views and profile-views only require the transchoice change and then it's ready for v1.0! Already got a branch ready to merge

The dutch language pack is another story though ...
And mybb-to-flarum doesn't require any change.

When it was said that 1.0 will bring breaking changes again, what must have been meant was: If you create really advanced, complex extensions with a ton of translations, they could break. Because my handful of extensions require no changes. Including my blatant copy of necrobumping that I recently published (expired posts). Which means necrobumping is compatible too.

Justoverclock i've noticed that i see a warning into console about:

index.js:36 Calling$.tooltipis now deprecated. Please use the<Tooltip>component exposed by flarum/core instead.$.tooltipmay be removed in a future version of Flarum.

but i have only one extension enabled, and i do not call old tooltip....so its related to core?

I see this too. Is it correct to assume that a warning like this is only showing due to this being a dev version of 1.0? Real 1.0 wouldn't spam a user's console, right? I have an unhealthy obsession with having a clean console on my production sites (zero warnings, zero errors).

010101 yeah, the same for me, i hate console log error .

but i think is only for dev version, you're right

010101 Because my handful of extensions require no changes. Including my blatant copy of necrobumping that I recently published (expired posts).

BTW, don't forget to tag a new version for 1.0

askvortsov If the composer constraint is set to beta 16 or above, do I need to change that? What is everyone setting the version constraints to this time around?

010101 "flarum/core": "^0.1.0" if I’m not mistaken

010101 You should probably use "flarum/core": "^0.1.0-beta.16 || ^1.0" if your extension works fine with both beta 16 and current 1.0.0-dev.

rob006 thanks a lot!

When opening the composer I see this in the console. Also, maybe unrelated, the insert link button is missing.

TypeError: this.navigator.when((function(){return e.active})).onUp is not a function. (In 'this.navigator.when((function(){return e.active})).onUp((function(){return e.navigate(-1)}))', 'this.navigator.when((function(){return e.active})).onUp' is undefined)

010101 this has been fixed, run composer update on this dev environment.

We've made a slight adjustment to make tagging new ext versions easier. If you have already followed the above steps, you'll need to change any instances of "0.1.x-dev" to "1.x.x-dev" in your composer.json version requirements for core and bundled extensions. Then, in your extensions, require flarum/core as ^1.0.0. Test that it works by running composer update again.