4. that was some weird formatting on the code section and it seems we don't get the nice formatting on some of them if there

that was some weird formatting on the code section and it seems we don't get the nice formatting on some of them if there


  • that was some weird formatting on the code section and it seems we don’t get the nice formatting on some of them if there

    • Sunday, December 1, 2019 @ 12:00:00 AM
      #AskRahula that was some weird formatting on the code section and it seems we don’t get the nice formatting on some of them if there isn’t an image.

    Let’s work on the formatting of the issues. I just updated the template for your content. Let’s see how that looks with it all put together now.

    I was riding a bike yesterday.

    This is just some content to see how the layouts work when we publish through the pipeline.

    When you go between systems that have their own packet formats sometimes a little fines is necessary to make it all come together.

    card.png

    Discord

    url: card.png
    link: Discord Message Link
    created: Sunday, December 1, 2019 @ 7:53:04 AM |

    Member
    🎳quinn#8461 Member Avatar 🎳quinn#8461
    joined: Friday, August 2, 2019 @ 10:13:46 AM

    Channel
    name: 🤖work
    topic: This is the work channel for Quinn Michaels. The stuff you see here should be taken as prototype and in progress. When you want a final product you will see me deliver from another channel.

    Guild
    FUN Guild Icon |—|
    name: FUN
    joined: Saturday, November 30, 2019 @ 8:08:12 AM
    members: 87
    invite: false

    Imgur

    that was some weird formatting on the code section and it seems we don’t get the nice formatting on some of them if there
    #AskRahula that was some weird formatting on the code section and it seems we don’t get the nice formatting on some of them if there isn’t an image.

    Let’s work on the formatting of the issues. I just updated the template for your content. Let’s see how that looks with it all put together now.

    I was riding a bike yesterday.

    This is just some content to see how the layouts work when we publish through the pipeline.

    When you go between systems that have their own packet formats sometimes a little fines is necessary to make it all come together.
    url: https://imgur.com/Cx75qCI
    created: Sunday, December 1, 2019 @ 12:00:00 AM

    Tweet

    RahulaClub avatar #AskRahula that was some weird formatting on the code section and it seems we don’t get the nice formatting on some of them if there isn’t an image.

    Let’s work on the formatting of the issues. I just updated the template for your content. by @quinnmichaels https://t.co/9jhlGc7Fli
    @RahulaClub
    link: https://twitter.com/RahulaClub/status/1201167406082609152
    hashtags: #AskRahula
    mentions:

    • @quinnmichaels "Follow quinnmichaels on Twitter"
      created: Sunday, December 1, 2019 @ 7:53:20 AM

    🖋 Authors

    @🎳quinn#8461

    🕵️‍♂️🕵️‍♂️Agents

    @RahulaClub

    $FEECTING: https://github.com/indraai/language-feecting/

    @authors >

    • @🎳quinn#8461

    @agents >

    @mentions >

    #hashes >
    #AskRahula

    – BEGIN:META

      Title: :title:
  Version: 0.3.3
  Author: :author_list:
  Date: :created:
  Copyright: Copyright 2019 (c) @🎳quinn#8461; All Rights Reserved
  License:
    Permission is hereby granted, free of charge, to any person obtaining a
    copy of this PROGRAM and associated documentation files (the "PROGRAM"),
    to deal in the PROGRAM without restriction, including without limitation
    the rights to use, copy, modify, merge, publish, distribute, sublicense,
    and/or sell copies of the PROGRAM, and to permit persons to whom the PROGRAM
    is furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included
    in all copies or substantial portions of the PROGRAM.

    THE PROGRAM IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
    OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
    THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
    OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
    ARISING FROM, OUT OF OR IN CONNECTION WITH THE PROGRAM OR THE USE OR
    OTHER DEALINGS IN THE PROGRAM.

    – END:META

    0
tyler 102