Skip to content

Conversation

ghost
Copy link

@ghost ghost commented Dec 30, 2017

I've added warnings about some procedures being deprecated.
Also I can't find what is the replacement for getTimezone proc, please help with that

Daniil Yarancev added 3 commits December 30, 2017 18:10
I've added warnings about some procedures being deprecated.
Also I can't find what is the replacement for `getTimezone` proc, please help with that
@dom96 dom96 merged commit a521f98 into devel Dec 30, 2017
@ghost
Copy link
Author

ghost commented Dec 30, 2017

@GULPF - can you please tell what is the replacement for getTimezone ?

@ghost ghost deleted the Yardanico-patch-1 branch December 30, 2017 15:16
@GULPF
Copy link
Member

GULPF commented Dec 30, 2017

This is incorrect - the replacement for toSeconds/fromSeconds is toUnix/fromUnix. Casting to/from Time will break when my current PR is merged, so it’s not a good idea (Time is spposed to be an opaque type).

getTimezone doesn’t have a direct replacement, as it does different things depending on backend/platform - one of the reasons why it’s deprecated.

@ghost
Copy link
Author

ghost commented Dec 30, 2017

@GULPF well I based warnings on proc code
Can you create a PR adding proper deprecation comments? You understand times better than me :)

@GULPF
Copy link
Member

GULPF commented Dec 31, 2017

@Yardanico No worries, I should have added the comments when I deprecated the procs. Fixed in #7005

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants