-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v1.0.0-rc] Remove deprecated features #2896
[v1.0.0-rc] Remove deprecated features #2896
Conversation
a3c1eac
to
ff10aee
Compare
Thank for getting this going @callingmedic911 @dac09 @peterp When do you think the timing is right for this one? Maybe v0.36, which will be within a couple of releases of v1-rc? |
Hi @callingmedic911 Thank you for your patience with us on this one. I had a discussion with the core team maintainers, and we would like to handle this is two parts:
Our thinking it that we don't want to create much resistance to people upgrading now. To Deprecate NowFor deprecations to include in our next release, I suggest:
To deprecate with v1.0.0-rc.0Then the remaining deprecation should happen along with the v1-rc release (along with anything else new that's scheduled for deprecation). What do you think of this plan? If it makes sense, just let me know how you want to split the PRs. Maybe just create a new PR for the commands deprecation and then pull the changes into this PR? Loop me in however needed. |
@thedavidprice I had a quick look of this PR, agreed and makes sense we should cherry-pick
Btw, just a kind reminding you might accidentally pasted the wrong PR number, just pointed out in case others get confused. :) |
@LBrian gah, fixed! (thank you... numbers are hard sometimes.) |
Totally agree.
I guess this also includes
I see @LBrian has cherry-picked 502159a and ff10aee. Thanks a lot @LBrian. :) I'll remove these commit from this PR now.
Sounds good! I'll use new |
Ah, I forgot to mention that we should skip anything api-server related for now. Peter has changes coming, so let's wait for those.
My mistake. I didn't mean to include that file. Let's skip for now 🤦♂️ Thanks! |
Got it. Thank you! |
8cafbf5
to
f9b4738
Compare
f9b4738
to
3a1ed4f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looping in others for specific questions.
Redwood-tools
I think it's time to fully deprecate redwood-tools.js
- packages/cli/src/redwood-tools.js
- references to
redwood-tools
andrwt
in packages/cli- including references in packages/cli/README.md
Agreed @dac09?
__REDWOOD__API_PROXY_PATH
Looks like we still have a reference to remove over here:
- packages/web/src/global.web-auto-imports.ts
Supabase.ts
@dthyresson do you have suggestions about how/if we should handle deprecations in:
- packages/auth/src/authClients/supabase.ts
?
Scaffold.js
@cannikin any reason not to fully deprecate this in v0.39?
redwood/packages/cli/src/commands/generate/scaffold/scaffold.js
Lines 692 to 697 in f129c58
/** @deprecated Used to be able to create dbAuth pages with `yarn rw g scaffold dbAuth` */ | |
if (modelArg.toLowerCase() === 'dbauth') { | |
console.info(c.green('\nGenerate dbAuth pages with:\n')) | |
console.info(' yarn rw generate dbAuth\n') | |
process.exit(0) | |
} |
processPagesDir
@peterp @dac09 Is this still an intended deprecation?
redwood/packages/internal/src/paths.ts
Lines 218 to 227 in f129c58
/** | |
* Process the pages directory and return information useful for automated imports. | |
* | |
* Note: glob.sync returns posix style paths on Windows machines | |
* @deprecated I will write a seperate method that use `getFiles` instead. This | |
* is used by structure, babel auto-importer and the eslint plugin. | |
*/ | |
export const processPagesDir = ( | |
webPagesDir: string = getPaths().web.pages | |
): Array<PagesDependency> => { |
Nope, go ahead and remove! I updated the docs recently to reference the new command |
Thanks for reviewing thoroughly @thedavidprice!
I'm not able to find any references to Apart from this, I have removed |
@thedavidprice for
I assume this question refers to: }): Promise<{
user: User | null
session: Session | null
error: Error | null
data: Session | User | null // Deprecated
}> to I'll check as that may no longer be in the current Supabase js sdk. |
FYI for Supabase, can upgrade to latest and then remove deprecations, but relies on a fix: supabase/auth-js#178 |
supabase/auth-js#179 has been merged, just need to await the next supabase-js release which I believe well be next week. |
@thedavidprice |
Finalizing and merging this now. Moved Supabase deprecation step to #3756 Release Notes: BreakingRouter GlobalsFully deprecates:
Use the following instead:
|
Closes #2631.
Before merging, maybe we want recheck:
EDIT 29th Sept 21:
Already removedbeforeResolver
is deprecated in v0.37.Update docsNot required anymore.This removes deprecated features planned for v1-rc.
Original:
I removed everything that says deprecated, even if it was marked deprecated only a few weeks ago. For example: 56f6019 (Supabase
data
field)Also, I made sure one commits maps to individual features, so it's a bit easier to review commit-wise and revert.
The only deprecated annotation left is - processPagesDir(), which we can remove once we have the suggested alternate implementation.
@dac09 @jtoar @thedavidprice