Skip to content
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

'XMonad.Actions.MessageFeedback': standardize #261

Merged
merged 1 commit into from
Jul 30, 2018

Conversation

orbisvicis
Copy link
Contributor

@orbisvicis orbisvicis commented Jun 13, 2018

  • Follow the naming conventions of XMonad.Operations. Functions returning
    X () are named regularly (previously these ended in underscore) while
    those returning X Bool are suffixed with an uppercase 'B'.

  • Provide all X Bool and SomeMessage variations for sendMessage and
    sendMessageWithNoRefresh, not just sendMessageWithNoRefreshToCurrent
    (renamed from send).

  • The new tryInOrderB and tryMessageB functions accept a parameter of
    type SomeMessage -> X Bool, which means you are no longer constrained
    to the behavior of the sendMessageWithNoRefreshToCurrent dispatcher.

  • The send*Messages* family of funtions allows for sequencing arbitrary
    sets of messages with minimal refresh. It makes little sense for these
    functions to support custom message dispatchers.

  • Remain backwards compatible. Maintain deprecated aliases of all renamed
    functions:

    • send -> sendMessageWithNoRefreshToCurrentB
    • sendSM -> sendSomeMessageWithNoRefreshToCurrentB
    • sendSM_ -> sendSomeMessageWithNoRefreshToCurrent
    • tryInOrder -> tryInOrderWithNoRefreshToCurrentB
    • tryInOrder_ -> tryInOrderWithNoRefreshToCurrent
    • tryMessage -> tryMessageWithNoRefreshToCurrentB
    • tryMessage_ -> tryMessageWithNoRefreshToCurrent

Description

Include a description for your changes, including the motivation
behind them.

Checklist

- Follow the naming conventions of `XMonad.Operations`. Functions returning
  `X ()` are named regularly (previously these ended in underscore) while
  those returning `X Bool` are suffixed with an uppercase 'B'.

- Provide all `X Bool` and `SomeMessage` variations for `sendMessage` and
  `sendMessageWithNoRefresh`, not just `sendMessageWithNoRefreshToCurrent`
  (renamed from `send`).

- The new `tryInOrderB` and `tryMessageB` functions accept a parameter of
  type `SomeMessage -> X Bool`, which means you are no longer constrained
  to the behavior of the `sendMessageWithNoRefreshToCurrent` dispatcher.

- The `send*Messages*` family of funtions allows for sequencing arbitrary
  sets of messages with minimal refresh. It makes little sense for these
  functions to support custom message dispatchers.

- Remain backwards compatible. Maintain deprecated aliases of all renamed
  functions:
  - `send`          -> `sendMessageWithNoRefreshToCurrentB`
  - `sendSM`        -> `sendSomeMessageWithNoRefreshToCurrentB`
  - `sendSM_`       -> `sendSomeMessageWithNoRefreshToCurrent`
  - `tryInOrder`    -> `tryInOrderWithNoRefreshToCurrentB`
  - `tryInOrder_`   -> `tryInOrderWithNoRefreshToCurrent`
  - `tryMessage`    -> `tryMessageWithNoRefreshToCurrentB`
  - `tryMessage_`   -> `tryMessageWithNoRefreshToCurrent`
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